Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1381

reference: 195-tree-1
name: 1381
tree-preservation-order: undefined
195-tpo-1
uprn
address-text
point: POINT (-1.031488 50.865177)
geometry: MULTIPOLYGON (((-1.031445 50.865172,-1.031447 50.865181,-1.031453 50.865188,-1.031462 50.865194,-1.031474 50.865198,-1.031487 50.865200,-1.031512 50.865195,-1.031522 50.865189,-1.031528 50.865181,-1.031530 50.865173,-1.031528 50.865165,-1.031523 50.865157,-1.031513 50.865151,-1.031501 50.865147,-1.031488 50.865146,-1.031475 50.865147,-1.031463 50.865151,-1.031454 50.865156,-1.031447 50.865164,-1.031445 50.865172)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL